import ChromeSlot from '@akinon/pz-theme/src/chrome/chrome-slot';
import { PLACEHOLDER_SLUGS } from '@akinon/pz-theme/src/chrome/placeholder-slugs';

/**
 * The screen the reset MAIL lands on, handed to the editor the same way its
 * two neighbours already are: the slot is an async server component and the
 * page is a client one, so the handover lives in the layout.
 *
 * A different page from the one that ASKS for the mail — that is
 * `users/password/reset` — and the last auth screen a brand could not compose:
 * `reset-password-body` was a slug the editor offered and nothing mounted, so a
 * designer could build the screen, publish it, and the shopper coming out of
 * their inbox still met the hand-written page.
 *
 * The token stays in the URL either way: this route's catch-all carries it, and
 * `reset-password-block` reads it back out of the segments (a token containing
 * slashes is joined, which a single segment would get wrong).
 *
 * With no composition published the slot renders the page untouched, so this
 * changes nothing until a brand composes the screen.
 */
export default function ResetPasswordLayout({
  children
}: {
  children: React.ReactNode;
}) {
  return (
    <ChromeSlot slug={PLACEHOLDER_SLUGS.resetPassword} fallback={children} />
  );
}